Internet Surfer 2.0/Internet Surfer 2.0 (Wayzata Technology) (1996).iso/pc/text/mac/faqs.549

Text File | 1996-02-12 | 27.9 KB | 537 lines

Frequently Asked Questions (FAQS);faqs.549


Affiliate of the Consortium is welcomed.
    Write to: Bob Scheifler, MIT X Consortium, Laboratory for Computer
Science, 545 Technology Square, Cambridge, MA 02139.

[For complete information see the XCONSORTIUM man page from the X11R4
distribution, from which this information is adapted.] [2/90]

----------------------------------------------------------------------
Subject:  12)  Just what are OPEN LOOK and Motif?

    OPEN LOOK and Motif are two graphical user interfaces (GUIs). OPEN LOOK
was developed by Sun with help from AT&T and many industry reviewers; Motif was
developed by the Open Software Foundation (OSF) with input from many OSF
members.

    OPEN LOOK is primarily a user-interface specification and style-guide;
there are several toolkits which can be used to produce OPEN LOOK applications.
Motif includes an API specification; the only sanctioned Motif toolkit is the
one from OSF. However, there are other toolkits which can be used to produce
programs which look and behave like OSF/Motif; one of these, ParcPlace's
(formerly Solbourne's) OI, is a "virtual toolkit" which provides objects in the
style of OPEN LOOK and Motif, at the user's choice.

    OPEN LOOK GUI is also the name of a product from AT&T, comprising
their OPEN LOOK Intrinsics Toolkit and a variety of applications.

[Thanks to Ian Darwin, [e-mail], 5/91]

----------------------------------------------------------------------
Subject:  13)  Just what is OpenWindows?

    Open Windows (3.0) is a Sun product that encompasses: a window system
that combines a NeWS and X11-compliant server (X/NeWS); a user-interface
specification (OPEN LOOK) and a series of toolkits that implement it (including
the SunView-like XView and the Xt-based OLIT); Xlib and Xt implementations; and
a number of utilities (olwm window manager, filemgr, shelltool, etc.).

[thanks to Frank Greco ([e-mail]), 8/90; 4/92]

----------------------------------------------------------------------
Subject:  14)  Just what is DECWindows?

    DECWindows is a DEC product that encompasses: an X11 server; the XUI
toolkit, including the Dwt widget set and UIL; Xlib and Xt implementations; a
session manager; and a number of utilities (dxwm window manager, dxcalendar,
dxpsview, etc.).

(At some point Motif flavors of the toolkit and applications will be shipped.)
[8/90]

----------------------------------------------------------------------
Subject:  15)  What is PEX?

    PEX is the "PHiGS Extension to X".
    PHiGS stands for "Programmer's Hierarchical Interactive Graphics
System" and is essentially a library of functions that simplifies the creation
and manipulation of 3D graphics. Many platforms are capable of performing in
hardware the computations involved in rendering 3D objects; the extension
allows the client (PHiGS in this case) to take advantage of the specialized
hardware for 3D graphics.
    Sun Microsystems is currently contracted to develop a freely
redistributable (copyright similar to the current X copyright) sample
implementation.  Source and documentation are available in the R5 release.
Several vendors are currently selling independently-developed PEX servers for
their workstations and X terminals.

[last modified 10/91]

----------------------------------------------------------------------
Subject:  16)  What is "low-bandwidth X" (LBX)? XRemote? PPP? SLIP? CSLIP?

There are several options for using X over serial lines:

SLIP - Serial Line IP; this is both a mechanism and a protocol for sending IP
packets over point-to-point serial links. It has been around for several years,
and implementations are available for many of the major TCP/IP implementations.
Most X Terminal vendors supply this as a checkoff item, although nobody really
ever uses it since it is horribly slow.  The TCP/IP headers add 40 bytes per
packet and the TCP/IP encoding of the X protocol is rather verbose (rightfully
so; it is optimized for packing and unpacking over high-speed links).

CSLIP - Compressed header SLIP; this is a variant of SLIP that compresses the 40
bytes of TCP/IP headers down to about 5 or 6 bytes.  It still doesn't do
anything about reencoding the X protocol.  Modems that do compression can help,
but they increase packet latency (it takes time to dribble the uncompressed data
through typical serial interfaces, plus the compression assembly time).

PPP - Point-to-Point Protocol; this is an emerging standard for point-to-point
links over serial lines that has a more complete set of option negotiation than
SLIP.  A growing number of people see the combination of PPP for the serial line
management and CSLIP for the header compression as becoming common for running
normal TCP/IP protocols over serial lines.  Running raw X over the wire still
needs compression somewhere to make it usable.

XRemote - this is the name of both a protocol and set of products originally
developed by NCD for squeezing the X protocol over serial lines.  In addition to
using a low level transport mechanism similar to PPP/CSLIP, XRemote removes
redundancies in the X protocol by sending deltas against previous packets and
using LZW to compress the entire data stream.  This work is done by either a
pseudo-X server or "proxy" running on the host or in a terminal server.  There
are several advantages to doing compression outside the modem:
   (1)    You don't *have* to have compressing modems in there if you wouldn't
    otherwise be using them (e.g. if you were going to be directly
    connected), and
   (2)    It reduces the I/O overhead by cutting down on the number of bytes that
    have to cross the serial interface, and
   (3)    In addition to the effects of #2, it reduces the latency in delivering
    packets by not requiring the modem to buffer up the data waiting for
    blocks to compress.

LBX - Low Bandwidth X; this is an X Consortium project that is working on a
standard for this area.  It is being chaired by NCD and Xerox and is using NCD's
XRemote protocol as a stepping stone in developing the new protocol.  LBX will
go beyond XRemote by adding proxy caching of commonly-used information (e.g.
connection setup data, large window properties, font metrics, keymaps, etc.) and
a more efficient encoding of the X protocol. The hope is to have a Standard
ready for public review in the first half of next year and a sample
implementation available in R6.

Additional technical information about how XRemote works and a few notes on how
LBX might be different are available via anonymous ftp from export.lcs.mit.edu
in contrib/ in the following files:
        XRemote-slides.ps               slides describing XRemote
        XRemote-LBX-diffs.ps            more slides describing some of LBX

[information provided by Jim Fulton, [e-mail]; 7/92]

----------------------------------------------------------------------
Subject:  17)  TOPIC: USING X IN DAY-TO-DAY LIFE
----------------------------------------------------------------------
Subject:  18)! What are all these different window managers?

    The window manager in X is just another client -- it is not part of the
X window system, although it enjoys special privileges -- and so there is
no single window manager; instead, there are many which support different ways
for the user to interact with windows and different styles of window layout,
decoration, and keyboard and colormap focus. In approximate chronological order
(generally, the more recent ones are more conformant with the ICCCM):

    wm: this simple title-bar window manager was phased out in R2 or R3
    uwm: the Universal Window Manager is still popular for its speed,
although it is very outdated. Moved to contrib/ on the R4 tape.
    twm (old): Tom's Window Manager was among the first non-MIT window
managers and offered the user a great deal of customization options in a
re-parenting window manager.
    awm: the Ardent Window Manager remains a hotbed for hackers and offers
some features (dynamic menus) not found on more current window managers
    cwm: cwm is part of the Andrew system.
    rtl: Siemen's window manager tiles windows so that they don't overlap
and resizes the window with the focus to its preferred size.
    dxwm: Digital's dxwm is part of the DECwindows offering
    hpwm: HP's window manager offers a 3D look; it is a precursor of mwm
    mwm: the Motif window manager is part of the OSF/Motif toolkit
    tekwm: Tektronix's window manager offering
    olwm (Sun): olwm implements the OPEN LOOK GUI and some of the Style
Guide functionality
    olwm (AT&T): ditto
    gwm: Bull's Generic Window Manager emulates others with a built-in
Lisp interpreter. Version 1.7h (10/91) is on the R5 contrib tape; 1.7m is on
avahi.inria.fr and export.lcs.mit.edu. [8/92]
    m_swm: the Sigma window manager is on the R4 tape
    pswm: Sun's PostScript-based pswm is part of the OpenWindows release
    swm: Solbourne's swm is based on the OI toolkit and offers multiple
GUI support and also a panned virtual window; configuration information comes
from the resources file
    twm (new): MIT's new Tab Window Manager from the R4 tape is a reworked
twm and is the basis for several derivatives, including the one on the R5 tape
    vtwm: vtwm offers some of the virtual-desktop features of swm, with a
single-root window implementation; it is based on the R4 twm and is available
on archive servers. A new version, vtwm-5.0, is based on R5.9 and is available
from export. [3/92]
    tvtwm: Tom's Virtual Tab Window Manager is also based on the R4 twm
and provides a virtual desktop modeled on the virtual-root window of swm. It is
available on archive servers
    olvwm: the vtwm-style virtual-desktop added to Sun's olwm. It is
available on archive servers; version 3.0 [1/92] is on export.
    mvwm: the vtwm-style virtual-desktop added to OSF's mwm. A beta version
is floating around (most recently from [e-mail]) but requires a
source license to OSF/Motif 1.1.3 [3/92].
    NCDwm: the window manager local to NCD terminals offers an mwm look
    XDSwm: the window manager local to Visual Technology's terminals
    ctwm: Claude Lecommandeur's ([e-mail]) modification of the R5
twm offers 32 virtual screens in the fashion of HP vuewm; source is on export.
Version 2.0 also offers the window overview used in vtwm and tvtwm.
    vuewm: HP's MWM-based window manager offers configurable workspaces.
    4Dwm: SGI's enhanced MWM

----------------------------------------------------------------------
Subject:  19)  Why does my X session exit when I kill my window manager (sic)?

    It needn't.  What is probably happening is that you are running your
window manager as the last job in your .xsession or .xinitrc file; your X
session runs only as long as the last job is running, and so killing your
window manager is equivalent to logging out. Instead, run the window manager in
the background, and as the last job instead invoke something safe like:
        exec xterm -name Login -rv -iconic
or any special client of your devising which exits on some user action.
Your X session will continue until you explicitly logout of this window,
whether or not you kill or restart your window manager.

----------------------------------------------------------------------
Subject:  20)  Can I save the state of my X session, like toolplaces does?

    Although no known window manager directly supports such a feature --
which may be equivalent to writing out a .xinitrc or .xsession file naming the
geometry and WM_COMMAND of each application (but olvwm may have something
close) -- there is a contributed application which does much of what you are
looking for, although it is not as complete as the SunView program toolplaces.
Look for the application "xplaces" on an archive-server near you. There are
several versions of this program floating around; look for a recent vintage.
[10/90]

----------------------------------------------------------------------
Subject:  21)  How do I use another window manager with DEC's session manager?

    DEC's session manager will start dxwm up by default. To override this,
add to your .Xdefaults file something like this line, naming the full pathname:
    sm.windowManagerName:   /wherever/usr/bin/X11/your_favorite_wm

----------------------------------------------------------------------
Subject:  22)  How do I change the keyboard auto-repeat rate?

    You can turn auto-repeat on or off by using "xset r on|off". The X
protocol, however, doesn't provide for varying the auto-repeat rate, which is
a capability not supported by all systems.
    Some servers running on systems that support this (the Xsun server from
MIT, for example), however, may provide command-line flags to set the rate at
start-up time. If you have control over server start-up, you can invoke the
server with the chosen settings.

----------------------------------------------------------------------
Subject:  23)  How do I remap the keys on my keyboard to produce a string?

    There is no method of arranging for a particular string to be
produced when you press a particular key. The xmodmap client, which is useful
for moving your CTRL and ESC keys to useful places, just rearranges keys and
does not do "macro expansion."
    Some (few) clients, including xterm and several X-based editors,
accept a translation resource such as:
    xterm*VT100.Translations: #override \
        <Key>F1: string("setenv DISPLAY unix:0")
which permits the shorthand F1 to be pressed to reset the display locally
within an xterm; it takes effect for new xterm clients. To include control
characters in the string, use \nnn, where nnn is the octal encoding of the
control character you want to include.
    Window managers, which could provide this facility, do not yet; nor
has a special "remapper" client been made available.

----------------------------------------------------------------------
Subject:  24)! How do I make a screendump or print my application?

    The xwd client in the X11 distributions can be used to select a window
or the background. It produces an XWD-format file of the image of that window.
The file can be post-processed into something useful or printed with the xpr
client and your local printing mechanism. You can use this command:
        csh% sleep 10; xwd -root > output.xwd &
and then spend 10 seconds or so setting up your screen; the entire current
display will be saved into the file output.xwd. Note that xwd also has an
undocumented (before R5) -id flag for specifying the window id on the
command-line. [There are also unofficial patches on export to xwd for
specifying the delay and the portion of the screen to capture.]

    Two publicly-available programs which allow interactive definition of
arbitrary portions of the display and built-in delays are asnap and xgrabsc.
There are several versions of xgrabsc; version 2.2, available on export [8/92]
is the most recent.
    xsnap includes some asnap features and supersedes it; it also renders
XPM output [version unknown]. It is available on export or avahi.inria.fr;
see xsnap-pl2.tar.Z.
    A screen-dump and merge/edit program combining features of xwd and xpr
is available from vernam.cs.uwm.edu as xdump1.0.tar.Z. Information:
[e-mail].

    To post-process the xwd output of some of these tools, you can use xpr,
which is part of the X11 distribution. Also on several archives are xwd2ps
and XtoPS, which produce Encapsulated PostScript with trimmings suitable for
use in presentations (see export.lcs.mit.edu:contrib/xwd2ps.tar.Z and
contrib/ImageMagick.tar.Z). Also useful is the PBMPLUS package on many archive
servers; and the Xim package contains Level 2 color PostScript output.

    Also:

    Bristol Technology ([e-mail], 203-438-6969) offers Xprinter
2.0, an Xlib API for PostScript and PCL printers; a demo is on ftp.uu.net
in vendor/Bristol/Xprinter.

    ColorSoft 9619-459-8500) offers OPENprint package includes a screen-
capture facility, image-processing, and support for PostScript and
non-PostScript printers.

    Some vendors' implementations of X (e.g. DECWindows and OpenWindows)
include session managers or other desktop programs which include "print portion
of screen" or "take a snapshot" options. Some platforms also have tools which
can be used to grab the frame-buffer directly; the Sun systems, for example,
have a 'screendump' program which produces a Sun raster file. Some X terminals
have local screen-dump utilities to write PostScript to a local serial printer.

    Some vendors' implementations of lpr (e.g. Sony) include direct
support for printing xwd files, but you'll typically need some other package
to massage the output into a useful format which you can get to the printer.

----------------------------------------------------------------------
Subject:  25)! How do I make a color PostScript screendump of the X display?

    If you need color PostScript in particular, you can
    - grab the screen-image using xgrabsc to begin with, which can produce
color PostScript.
    - grab the screen-image using xwd and post-process xwd into color PS.
You can do this using xwd2ps or the XtoPS program from the ImageMagick
distribution. The PBMPLUS package is also good for this, as is the Xim package.

----------------------------------------------------------------------
Subject:  26)  How do I make a screendump including the X cursor?

    This can't be done unless the X server has been extended. Consider
instead a system-dependent mechanism for, e.g.,  capturing the frame-buffer.

----------------------------------------------------------------------
Subject:  27)! How do I convert/view Mac/TIFF/GIF/Sun/PICT/img/FAX images in X?

    The likeliest program is an incarnation of Jef Poskanzer's useful++
Portable Bitmap Toolkit, which includes a number of programs for converting
among various image formats. It includes support for many types of bitmaps,
gray-scale images, and full-color images. PBMPLUS has been updated recently;
the most recent version [12/91] is on export in contrib/pbmplus10dec91.tar.Z.
    Another tool is San Diego Supercomputing Center's IMtools ('imconv' in
particular), which packages the functionality of PBM into a single binary.
It's available anonymous ftp from sdsc.edu (132.249.20.22).

    Useful for viewing some image-formats is Jim Frost's xloadimage, a
version of which is in the R4 directory contrib/clients/xloadimage; there are
later versions available, including contrib/xloadimage.3.03.tar.Z on export.
Graeme Gill's updates to an earlier version of xloadimage are also on export;
see xli.README and xli.tar.Z.uu.

    An alternate image-viewer is xv (X Image Viewer), written by
[e-mail] (John Bradley). XV displays many image formats and
permits editing of GIF files, among others. The program was updated 5/92; see
the file contrib/xv-2.21.tar.Z on export.lcs.mit.edu.

    The Fuzzy Pixmap Manipulation, by Michael Mauldin <[e-mail]>.
Conversion and manipulation package, similar to PBMPLUS.  Version 1.0 available
via FTP as nl.cs.cmu.edu:/usr/mlm/ftp/fbm.tar.Z, uunet.uu.net:pub/fbm.tar.Z,
and ucsd.edu:graphics/fbm.tar.Z.

    The Img Software Set, by Paul Raveling <[e-mail]>, reads
and writes its own image format, displays on an X11 screen, and does some image
manipulations.  Version 1.3 is available via FTP on expo.lcs.mit.edu as
contrib/img_1.3.tar.Z, along with large collection of color images.

    The Utah RLE Toolkit is a conversion and manipulation package similar
to PBMPLUS.  Available via FTP as cs.utah.edu:pub/urt-*,
weedeater.math.yale.edu:pub/urt-*, and freebie.engin.umich.edu:pub/urt-*.

    Xim, The X Image Manipulator, by Philip Thompson, does essential
interactive displaying, editing, filtering, and converting of images. There is
a version in the X11R4 contrib area; but a more recent version (using R4 and
Motif 1.1) is available from gis.mit.edu (18.80.1.118). Xim reads/writes gif,
xwd, xbm, tiff, rle, xim, (writes level 2 eps) and other formats and also has a
library and command-line utilities for building your own applications.

    ImageMagick [2.1b] by [e-mail] can be retrieved from export's
contrib area. It is a collection of utilities to transform and display images
on any X server. The tool uses the MIFF format; filters to and from MIFF from
other popular formats (PPM, TIFF, GIF, SUN Raster, etc) are included.

    xtiff is a tool for viewing a TIFF file in an X window.  It was written
to handle as many different kinds of TIFF files as possible while remaining
simple, portable and efficient.  xtiff illustrates some common problems
with building pixmaps and using different visual classes.  It is distributed
as part of Sam Leffler's libtiff package and it is also available on
export.lcs.mit.edu, uunet.uu.net and comp.sources.x. [[e-mail],10/90]
xtiff 2.0 was announced in 4/91; it includes Xlib and Xt versions.

    A version of Lee Iverson's ([e-mail]) image-viewing tool
is available as contrib/vimage-0.9.3.tar.Z on export.lcs.mit.edu.  The package
also includes an ImageViewPort widget and a FileDialog widget. [12/91;5/92]

[some material from Larry Carroll ([e-mail]), 5/91]

----------------------------------------------------------------------
Subject:  28)  How can I change the titlebar of my xterm window?

    The solution involves sending an escape sequence to xterm which will
cause it to update the property which the window manager relies upon for the
string which appears in the window titlebar.
    A solution is as easy as typing this in an xterm running a shell:
        echo "ESC]2;TEXT^G"
where ESC is the escape key, TEXT is the string you wish to have displayed,
and ^G is a Control-G (the BEL character).

    Here is a more complicated csh alias which changes the titlebar to
the current working directory when you change directories:
        alias newcd 'cd \!*; echo -n ESC]2\;$cwd^G'

    The digit '2' in these strings indicates to xterm that it should
change only the title of the window; to change both the title and the name
used in the icon, use the digit '0' instead, and use '1' to change only the
icon name.

    Note: another way to do this, which prevents an incorrect display of
the local directory if a modified `cd` is used in a subshell, is to wrap the
escape sequences into the PS1 prompt itself.

    Note: on an IBM RS/6000 is may be necessary to begin the sequence with
a ^V.

----------------------------------------------------------------------
Subject:  29)  Where can I find the xterm control sequences?

The best source of such information is in your R5 sources in the file
ctlseqs.ms; a PostScript version is in mit/hardcopy/clients/ctlseqs.PS.Z.

Other good sources of information include the R4 version of that document
and also the file in the R4 sources called mit/clients/xterm/ctlseq2.txt, a
compilation put together by Skip Montanaro (GE CR&D) listing the VT100
sequences. It dates from R3 but is fairly accurate.  A hardcopy version was
published in the December 1989 XNextEvent (the XUG newsletter).

In addition, Volume 3 (User's Guide) of the R4 flavor of the O'Reilly
X Window System series contains an appendix listing xterm control sequences;
it is less accurate than the information in the R5 or R4 sources.

In a pinch, a VT100 manual will do.

[last updated 10/91]

----------------------------------------------------------------------
Subject:  30)  Why does the R3 xterm, et al, fail against the R4 server?

    The value given to a window's do_not_propagate mask is the likely
culprit.  R3 allowed bogus values to be set, and early version of both Andrew
and InterViews did, as well. Similar problems also occur in the R3 Motif
PanedWindow widget.
    If it is impossible to fix client source -- and many systems still ship
the R3 xterm -- use 'xset bc' to put the X11R4 server into bug-compatibility
mode.

----------------------------------------------------------------------
Subject:  31)  How can I use characters above ASCII 127 in xterm ?

    In order to use special characters such as the o-umlaut, you need to
"stty pass8" but also to use a charcell ISO8859 font, such as
    XTerm*font:     -*-*-medium-r-normal-*-*-130-*-*-c-*-iso8859-1
    XTerm*boldfont:    -*-*-bold-r-normal-*-*-130-*-*-c-*-iso8859-1
[The family is intentionally unspecified in this example.]

In addition, you may want to set this in your shell:
    setenv LC_CTYPE iso_8859_1

        For a given character above 127, you can determine the key to use with
the Alt modifier by finding the equivalent character below 127 (try using
`man ascii`). For example, o-umlaut (v) is Alt-v and the section character (')
is Alt-'.

[thanks to Greg Holmberg ([e-mail]) and Stephen Gildea
([e-mail]); 6/92]

----------------------------------------------------------------------
Subject:  32)  Why are my xterm menus so small?

    You are probably setting the geometry small accidentally. If you give
a resource specification like this:
        xterm*geometry: 80x24
then you are asking for all widgets under xterm to have their geometry set to
80x24. For the main window, this is OK, as it uses characters for its size.
But its popup menus don't; they are in pixels and show up small. To set only
the terminal widget to have the specified geometry, name it explicitly:
        xterm*VT100.geometry: 80x24

----------------------------------------------------------------------
Subject:  33)  How can I print the current selection?

    You could paste it into an xterm after executing the lpr command.
However, a program by Richard Hesketh ([e-mail]) specifically for
manipulating the selection will help; e.g.
    % xselection PRIMARY | lpr
finds the primary selection and prints it. This command can be placed in a
window-manager menu or in shell-scripts. xselection also permits the setting of
the selection and other properties. A version is on export.
    Also available is ria.ccs.uwo.ca:pub/xget_selection.tar.Z, which can be
adapted to do this.

----------------------------------------------------------------------
Subject:  34)  How does Xt use environment variables in loading resources?

    You can use several environment variables to control how resources are
loaded for your Xt-based programs -- XFILESEARCHPATH, XUSERFILESEARCHPATH, and
XAPPLRESDIR.  These environment variables control where Xt looks for
application-defaults files as an application is initializing.  Xt loads at most
one app-defaults file from the path defined in XFILESEARCHPATH and another from
the path defined in XUSERFILESEARCHPATH.

    Set XFILESEARCHPATH if software is installed on your system in such a
way that app-defaults files appear in several different directory hierarchies.
Suppose, for example, that you are running Sun's Open Windows, and you also
have some R4 X applications installed in /usr/lib/X11/app-defaults. You could
set a value like this for XFILESEARCHPATH, and it would cause Xt to look up
app-defaults files in both /usr/lib/X11 and /usr/openwin/lib (or wherever your
OPENWINHOME is located):
    setenv XFILESEARCHPATH /usr/lib/X11/%T/%N:$OPENWINHOME/lib/%T/%N

    The value of this environment variable is a colon-separated list of
pathnames.  The pathnames contain replacement characters as follows:
    %T        the literal string "app-defaults" [works only in
            XFILESEARCHPATH]
    %N        application class name
    %C        customization resource (R5 only)
    %L        language, locale, and codeset (e.g. "ja_JP.EUC")
    %l        language part of %L  (e.g. "ja")

    Let's take apart the example.  Suppose the application's class name is
"Myterm". Also, suppose Open Windows is installed in /usr/openwin. (Notice the
example omits locale-specific lookup.)
    /usr/lib/X11/%T/%N        means /usr/lib/X11/app-defaults/Myterm
    $OPENWINHOME/lib/%T/%N    means /usr/openwin/lib/app-defaults/Myterm

    As the application initializes, Xt tries to open both of the above
app-defaults files, in the order shown.  As soon as it finds one, it reads it
and uses it, and stops looking for others.  The effect of this path is to
search first in /usr/lib/X11, then in /usr/openwin.

    Let's consider another example. This time, let's set
XUSERFILESEARCHPATH so it looks for the file Myterm.ad in the current working
directory, then for Myterm in the directory ~/app-defaults.
    setenv XUSERFILESEARCHPATH ./%N.ad:$HOME/app-defaults/%N

    The first path in the list expands to ./Myterm.ad.  The second expands
to $HOME/app-defaults/Myterm.  This is a convenient setting for debugging
because it follows the Imake convention of naming the app-defaults file
Myterm.ad in the application's source directory, so you can run the application
from the directory in which you are working and still have the resources loaded
properly.